Method and system for multi-dimensional raid

ABSTRACT

A method for storing data including calculating: a first set of parity values using the data, a second set of parity values using the first set of parity values, and a third set of parity values using the data, and the first set and second set of parity values. The method further includes storing a portion of the data in a grid, where the grid includes grids locations that are each associated with a physical location, where each physical location is determined using a unique combination of at least a first value determined using a first independent fault domain and a second value determined using a second independent fault domain. The method further includes storing parity values from the first set of parity values and parity values from the second set of parity values in the grid, and storing the third set of parity values in an associated parity grid.

BACKGROUND

In order to protect against potential loss of data in a storage system,it is often advantageous to implement a replication scheme. Currentreplication schemes are only able to sustain a limited amount of errorbefore data within the storage system is unable to be read.

SUMMARY

In general, in one aspect, the invention relates to a method for storingdata. The method includes receiving a request to write data, in responsethe request, selecting, a RAID grid location in a RAID grid to write thedata, writing the data to memory, wherein the data is temporarily storedin the memory, updating a data structure to indicate that the RAID gridlocation is filled, determining, using the data structure, whether adata grid in the RAID grid is filled, wherein the RAID grid location isin the data grid, based on a determination that the data grid is filled:calculating parity values for the RAID grid using the data determining aphysical address in persistent storage corresponding to the RAID gridlocation, writing the data to a physical location in persistent storagecorresponding to the physical address, and writing the parity values tothe persistent storage.

In general, in one aspect, the invention relates to a method forreconstructing data. The method includes receiving a request for firstdata, obtaining the first data, wherein the first data is obtained froma first physical location in persistent storage and wherein the firstphysical location is associated with a first physical address, making afirst determination that the first data is one selected from a groupconsisting of corrupted and not obtained, based on the firstdetermination: identifying a first RAID grid location corresponding tothe first physical address, identifying that a first RAID grid isassociated with the first RAID grid location, identifying a RAID cubeassociated with the first RAID grid, wherein the RAID cube comprises thefirst RAID grid and a second RAID grid, making a first attempt toreconstruct the first data using at least one value in the first RAIDgrid, wherein the first attempt fails, making a second attempt, afterthe first attempt fails, to reconstruct the first data using at leastone value in the second RAID grid, wherein the second attempt issuccessful, and providing the reconstructed first data to the client.

In general, in one aspect, the invention relates to a method forreconstructing data. The method includes receiving a request for data,obtaining the data, wherein the data is obtained from a physicallocation in persistent storage and wherein the physical location isassociated with a physical address, making a first determination thatthe first data is one selected from a group consisting of corrupted andnot obtained, based on the first determination: identifying a first RAIDgrid location corresponding to the physical address, identifying that aRAID grid is associated with the first RAID grid location, making afirst attempt to reconstruct the data using a first value in a secondRAID grid location, wherein the second RAID grid location is located inat least one selected from a group consisting of a first row and a firstcolumn in the RAID grid, wherein the first RAID grid location is part ofthe first row and the first column, wherein the first attempt fails,making a second attempt, after the first attempt fails, to reconstructthe data, wherein the second attempt is successful and wherein thesecond attempt comprises: reconstructing at least one selected from agroup consisting of a second row and a second column in the RAID grid toobtain a reconstructed portion of the RAID grid, wherein thereconstructed portion of the RAID grid intersects at least one selectedfrom a group consisting of the first row and the first column,reconstructing the data using a second value in a third RAID gridlocation, wherein the third RAID grid location is part of thereconstructed portion of the RAID grid, and wherein the third RAID gridlocation is located in one selected from a group consisting of the firstrow and first column, and providing the reconstructed data to theclient.

Other aspects of the invention will be apparent from the followingdescription and the appended claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a system in accordance with one embodiment of theinvention.

FIG. 2 shows a RAID grid in accordance with one embodiment of theinvention.

FIG. 3 shows a RAID cube and various view of the RAID cube in accordancewith one embodiment of the invention.

FIG. 4 shows a data structures in accordance with one embodiment of theinvention.

FIGS. 5A-5C show flow charts in accordance with one embodiment of theinvention.

FIGS. 6A-6C show an example in accordance with one or more embodimentsof the invention.

FIGS. 7A-7D show an example in accordance with one or more embodimentsof the invention.

FIG. 8. shows a flow chart in accordance with one or more embodiments ofthe invention.

FIGS. 9A-9D show an example in accordance with one or more embodimentsof the invention.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detailwith reference to the accompanying figures. In the following detaileddescription of embodiments of the invention, numerous specific detailsare set forth in order to provide a more thorough understanding of theinvention. However, it will be apparent to one of ordinary skill in theart that the invention may be practiced without these specific details.In other instances, well-known features have not been described indetail to avoid unnecessarily complicating the description.

In the following description of FIGS. 1-9D, any component described withregard to a figure, in various embodiments of the invention, may beequivalent to one or more like-named components described with regard toany other figure. For brevity, descriptions of these components will notbe repeated with regard to each figure. Thus, each and every embodimentof the components of each figure is incorporated by reference andassumed to be optionally present within every other figure having one ormore like-named components. Additionally, in accordance with variousembodiments of the invention, any description of the components of afigure is to be interpreted as an optional embodiment which may beimplemented in addition to, in conjunction with, or in place of theembodiments described with regard to a corresponding like-namedcomponent in any other figure.

In general, embodiments of the invention relate to a method and systemfor replicating data using a multi-dimensional RAID scheme. Morespecifically, embodiments of the invention provide a method and systemfor implementing a 2D RAID scheme and a 3D RAID scheme.

Using a 2D RAID scheme, the data stored within a RAID grid implementingsuch a RAID scheme may be recovered when there are more than two errorsin a given RAID stripe. Similarly, using a 3D RAID scheme, the datastored within a RAID cube implementing such a RAID scheme may berecovered when there are more than two errors in a given RAID stripe.Further, in various embodiments of the invention, all data is to berecovered when there is a failure in more than one independent faultdomain (IFD).

In one or more embodiments of the invention, an IFD corresponds to afailure mode which results in the data at a given location beinginaccessible. Each IFD corresponds to an independent mode of failure inthe storage array. For example, if the data is stored in NAND flash,where the NAND flash is part of a storage module (which includesmultiple NAND dies), then the IFDs may be (i) storage module, (ii)channel (i.e., the channel used by the storage module controller (notshown) in the storage module to write data to the NAND flash), and (iii)NAND die.

For purposes of this invention, the term “RAID” as used herein refers to“Redundant Array of Independent Disks.” While “RAID” refers to any arrayof independent disks, embodiments of the invention may be implementedusing any type of persistent storage device where the RAID gridlocations (see e.g., FIG. 2) may be distributed across one or morepersistent storage devices based on the implementation of the invention(see e.g., FIGS. 3 and 4).

FIG. 1 shows a system in accordance with one embodiment of theinvention. As shown in FIG. 1, the system includes one or more clients(100A, 100M), a RAID controller (104), memory (106), optionally an FPGA(102), and a storage array (108).

In one embodiment of the invention, a client (100A, 100M) is any systemor process executing on a system that includes functionality to issue aread request or a write request to the RAID controller (104). In oneembodiment of the invention, the clients (100A, 100M) may each include aprocessor (not shown), memory (not shown), and persistent storage (notshown). In one embodiment of the invention, the RAID controller (104) isconfigured to implement the multi-dimensional RAID scheme, whichincludes writing data to the storage array in a manner consistent withthe multi-dimensional RAID scheme (see FIG. 5A-5C) and reading data(including reconstructing data) from the storage array in a mannerconsistent with the multi-dimensional RAID scheme (see FIG. 8). In oneembodiment of the invention, the RAID controller (104) includes aprocessor configured to execute instructions to implement one or moreembodiments of the invention, where the instructions are stored on anon-transitory computer readable medium (not shown) that is locatedwithin or that is operatively connected to the RAID controller (104).Alternatively, the RAID controller (104) may be implemented usinghardware. Those skilled in the art will appreciate that the RAIDcontroller (104) may be implemented using any combination of softwareand/or hardware.

In one embodiment of the invention, the RAID controller (104) isoperatively connected to memory (106). The memory (106) may be anyvolatile memory including, but not limited to, Dynamic Random-AccessMemory (DRAM), Synchronous DRAM, SDR SDRAM, and DDR SDRAM. In oneembodiment of the invention, the memory (106) is configured totemporarily store various data (including parity data) prior to suchdata being stored in the storage array.

In one embodiment of the invention, the FPGA (102) (if present) includesfunctionality to calculate P and/or Q parity information for purposes ofstoring data in the storage array (108) and/or functionality to performvarious calculations necessary to recover corrupted data stored usingthe multi-dimensional RAID scheme. The RAID controller (104) may use theFPGA (102) to offload the processing of various data in accordance withone or more embodiments of the invention. In one embodiment of theinvention, the storage array (108) includes a number of individualpersistent storage devices including, but not limited to, magneticmemory devices, optical memory devices, solid state memory devices,phase change memory devices, any other suitable type of persistentmemory device, or any combination thereof.

Those skilled in the art will appreciate that while FIG. 1 shows anFPGA, the invention may be implemented without an FPGA. Further, thoseskilled in the art will appreciate that other components may be used inplace of the FPGA without departing from the invention. For example, theinvention may be implemented using an ASIC(s), a graphics processingunit(s) (GPU), a general purpose processor(s), any other hardware devicecapable of calculating P and/or Q parity information for purposes ofstoring data in the storage array and/or performing various calculationsnecessary to recover corrupted data stored using the multi-dimensionalRAID scheme, any devices that includes a combination of hardware,firmware, and/or software configured to calculate P and/or Q parityinformation for purposes of storing data in the storage array (108)and/or to perform various calculations necessary to recover corrupteddata stored using the multi-dimensional RAID scheme, or any combinationthereof.

FIG. 2 shows a RAID grid in accordance with one embodiment of theinvention. In one embodiment of the invention, if the RAID controllerimplements a 2D RAID scheme or a 3D RAID scheme (see FIG. 3), the RAIDcontroller stores data in a RAID Grid (200). FIG. 2 shows the conceptualportions of a RAID grid in accordance with one or more embodiments ofthe invention. The RAID grid (200) includes a number of RAID gridlocations, where each RAID grid location is ultimately written to aunique physical address in the storage array. The RAID grid (200)includes (i) a data grid (202), which includes RAID grid locations thatstore data received from the client (i.e., data that the client hasinstructed the RAID controller to write to the storage array; (ii) a rowP parity group (204), which includes the RAID grid locations that storein the P parity values calculated using data in RAID grid locations in arow (described below); (iii) a row Q parity group (206), which includesthe RAID grid locations that store in the Q parity values calculatedusing data in RAID grid locations in a row (described below); (iv) acolumn P parity group (208), which includes the RAID grid locations thatstore in the P parity values calculated using data in RAID gridlocations in a column (described below); (v) a column Q parity group(210), which includes the RAID grid locations that store in the Q parityvalues calculated using data in RAID grid locations in a column(described below); and (vi) an intersection parity group (212), whichincludes parity values calculated using (a) data from RAID gridlocations in row P parity group (204), (b) data from RAID grid locationsin row Q parity group (206), (c) data from RAID grid locations in columnP parity group (208), and (d) data from RAID grid locations in column Qparity group (210) (described below).

Referring to row (214), in one embodiment of the invention, the datastored in RAID grid location denoted as P_(r) in row (214) is calculatedby applying a P parity function to all RAID grid locations in the row(214) that includes data (e.g., P_(r)=f_(P) (D₁, D₂, D₃, D₄). Similarly,in one embodiment of the invention, the data stored in RAID gridlocation denoted as Q_(r) in row (214) is calculated by applying a Qparity function to all RAID grid locations in the row (214) thatincludes data (e.g., Q_(r)=f_(Q) (D₁, D₂, D₃, D₄).

Referring to column (216), in one embodiment of the invention, datastored in the RAID grid location denoted as P_(C) in column (216) iscalculated by applying a P parity function to all RAID grid locations inthe column (216) that includes data (e.g., P_(C)=f_(P) (D₅, D₂, D₆, D₇).Similarly, in one embodiment of the invention, data stored in the RAIDgrid location denotes by Q_(C) in column (216) is calculated by applyinga Q parity function to all RAID grid locations in the column (216) thatincludes data (e.g., Q_(C)=f_(Q)(D₅, D₂, D₆, D₇).

Referring to the intersection parity group (212), in one embodiment ofthe invention, the data stored in the RAID grid location denoted asI_(r1) may be calculated by applying a P parity function to all RAIDgrid locations in the row P Parity Group (204) or by applying a P parityfunction to all RAID grid locations in the column P Parity Group (208).For example, I_(r1)=f_(P) (P_(r1), P_(r2), P_(r3), P_(r4)) orI_(r1)=f_(P)(P_(c5), P_(c6), P_(c7), P_(c8)).

In one embodiment of the invention, the data stored in the RAID gridlocation denoted as I_(r2) may be calculated by applying a P parityfunction to all RAID grid locations in the row Q Parity Group (204) orby applying a Q parity function to all RAID grid locations in the columnP Parity Group (208). For example, I_(r2)=f_(P) (Q_(r1), Q_(r2), Q_(r3),Q_(r4)) or I_(r2)=f_(Q) (P_(c5), P_(c6), P_(c7), P_(c8)).

In one embodiment of the invention, the data stored in the RAID gridlocation denoted as I_(r3) may be calculated by applying a P parityfunction to all RAID grid locations in the column Q Parity Group (210)or by applying a Q parity function to all RAID grid locations in the rowP Parity Group (204). For example, I_(r3)=f_(P) (Q_(c5), Q_(c6), Q_(c7),Q_(c8)) or I_(r3)=f_(Q) (P_(c1), P_(c2), P_(c3), P_(c4)).

In one embodiment of the invention, the data stored in the RAID gridlocation denoted as I_(r4) may be calculated by applying a Q parityfunction to all RAID grid locations in the column Q Parity Group (210)or by applying a Q parity function to all RAID grid locations in the rowQ Parity Group (206). For example, I_(r4)=f_(Q) (Q_(c1), Q_(c2), Q_(c3),Q_(c4)) or I_(r4)=f_(Q) (Q_(c5), Q_(c6), Q_(c7), Q_(c8)).

In one embodiment of the invention, the P and Q parity functions used tocalculate the values for all of parity groups may correspond to any Pand Q parity functions used to implement RAID 6.

As discussed above, the RAID grid (200) shown in FIG. 2 represents theconceptual layout of a RAID grid. However, when the individual RAID gridlocations are written to the storage array, the relative location of thevarious RAID grid locations may vary across a row and or a column. Forexample, referring to row (214), when the RAID grid locations within row(214) are written to the storage array, the relative location of RAIDgrid locations that include data (denoted by “D”) and the RAID gridlocations that include parity data (i.e., the RAID grid locationsdenoted as “P_(r)” and “Q_(r)”) may be as follows: <D₁, D₂ P_(r2), D₃Q_(r2), D₄>, <P_(r2), Q_(r2), D₁, D₂, D₃, D₄>, or any other arrangementwithin row (214). Similarly, referring to column (216), the relativelocation of RAID grid locations that include data (denoted by “D”) andthe RAID grid locations that include parity data (i.e., the RAID gridlocations denoted as “P_(c)” and “Q_(c)”) may be as follows: <D₅, D₂,D₆, P_(c6), D₆, Q_(c6)>, <P_(c6), D₅, D₂, Q_(c6), D₆, D₇>, or any otherarrangement within column (216).

The RAID controller (or another entity in the system) may determine towhich physical addresses in the storage array each of the RAID gridlocations is written. This determination may be made prior to receivingany of the data (denoted as “D”) for a particular RAID grid from theclient. Alternatively, the determination may be made prior to writingthe RAID grid locations to the storage array.

Those skilled in the art will appreciate that while FIG. 2 shows a RAIDgrid that is 6×6, the RAID grid may be implemented using any otherdimensions without departing from the invention.

In one embodiment of the invention, the P parity value is a Reed-Solomonsyndrome and, as such, the P Parity function may correspond to anyfunction that can generate a Reed-Solomon syndrome. In one embodiment ofthe invention, the P parity function is an XOR function.

In one embodiment of the invention, the Q parity value is a Reed-Solomonsyndrome and, as such, the Q Parity function may correspond to anyfunction that can generate a Reed-Solomon syndrome. In one embodiment ofthe invention, a Q parity value is a Reed-Solomon code. In oneembodiment of the invention,Q=g⁰·D₀+g¹·D₁+g²·D_(2+ . . . +)g^(n-1)·D_(n-1), where Q corresponds anyone of the Q parity values defined with respect to FIG. 2, g is agenerator of the field, and the value of D corresponds to the data(which may include both values from the data grid and/or values from oneor more rows or columns that include P or Q parity values).

Those skilled in the art will appreciate that while the RAID grid inFIG. 2 includes P and Q parity for each row and column, embodiments ofthe invention may be implemented using greater or fewer parity valueswithout departing from the invention. For example, each row and columnmay only include a P parity value. In another example, each row andcolumn may include three parity values. The aforementioned examples arenot intended to limit the invention. In one embodiment of the invention,regardless of the number of parity values used in the implementation ofthe invention, each of the parity values is a Reed-Solomon syndrome.

FIG. 3 shows a RAID cube and various views of the RAID cube inaccordance with one embodiment of the invention. As shown in FIG. 3, aRAID cube (300) corresponds to a conceptual stack of RAID grids (302).As discussed above, the RAID controller (or another entity in thesystem) selects the physical addresses within the storage array in whichto store the data for each of the RAID grid locations. In one embodimentof the invention, the selection of the physical addresses may bedetermined in accordance with the IFDs for which the RAID grid (or RAIDcube) is designed to protect against. Said another way, the physicaladdresses may be selected in a manner to protect against failures in oneor more IFDs. For example, as shown in FIG. 3, each RAID grid location(not shown) for a given RAID grid (302, 304) is written to a physicaladdress (or will be written to a physical address) in the storage array(not shown) that is selected using a unique pair of values from IFD 1and IFD 2, but has the same value for IFD 3. For example, if the data inthe storage array is stored in NAND flash, where the NAND flash is partof a storage module (which includes multiple NAND dies), then the IFDsmay be as follows: (i) IFD 1=storage module, (ii) IFD [[1]] 2=channel,and (iii) IFD 3=NAND die. Accordingly, in a given RAID grid, the data ineach RAID grid location is written to a unique combination of storagemodule (IFD 1) and channel (IFD 2) but is written to the same NAND die(on each of the storage modules). Those skilled in the art willappreciate that the invention is not limited to the three independentfault domains described above. Further, those skilled in the art willappreciate that the invention is not limited to a storage array thatincludes NAND flash.

Continuing with FIG. 3, as discussed above, the RAID cube (300) isconceptual stack of RAID grids. More specifically, in one embodiment ofthe invention, the RAID cube (300) may include (i) a data portion (316),which includes two or more RAID grids (304, 306, 308, 310) (see FIG. 2)and a parity portion (318) that includes a P parity RAID grid (312) anda Q parity RAID grid (314).

In one embodiment of the invention, the RAID grids (304, 306, 308, 310)in the data portion (316) include parity data (see FIG. 2), which allowsdata within the RAID grid to be recovered using only data (includingparity data) within the RAID grid. In one embodiment of the invention,the RAID cube is arranged such that data for a given RAID grid locationin a given RAID grid (304, 306, 308, 310) may be recovered using data(including parity data) from other RAID grids (in both the data portion(316) and the parity portion (318). In one embodiment of the invention,the parity portion (318) of the RAID cube enables such a recoverymechanism.

In one embodiment of the invention, the P parity RAID grid (312) is thesame dimension as the underlying RAID grids (304, 306, 308, 310), wherethe data in every RAID grid location within the P Parity RAID grid iscalculated by applying a P parity function (e.g., an XOR function) todata (including parity data) from the RAID grids in the data portion(316) (see FIG. 7) Similarly, the Q parity RAID grid (314) is the samedimension as the underlying RAID grids (304, 306, 308, 310), where thedata in every RAID grid location within the Q Parity RAID grid iscalculated by applying a Q parity function to data (including paritydata) from the RAID grids in the data portion (316) (see FIG. 7).

FIG. 4 shows data structures in accordance with one embodiment of theinvention. In one embodiment of the invention, the RAID controllerincludes one or more data structures to implement the multi-dimensionalRAID schemes.

In one embodiment of the invention, the RAID controller includes a datastructure that tracks the mappings between data provided by the clientand the physical address of such data in the storage array. In oneembodiment of the invention, the RAID controller tracks theaforementioned information using a mapping between a logical addresse.g., <object, offset> (400), which identifies the data from theperspective of the client, and physical address (402), which identifiesthe location of the data within the storage array. In one embodiment ofthe invention, the mapping may be between a hash value derived fromapplying a hash function (e.g., MD5, SHA 1) to <object, offset>. Thoseskilled in the art will appreciate that any form of logical address maybe used without departing the invention.

In one embodiment of the invention, the RAID controller includes a datastructure that tracks how each RAID grid location (404) (see FIG. 2) ismapped to a particular physical address (402) in the storage array.

In one embodiment of the invention, the RAID controller includes a datastructure that tracks which RAID grid (including RAID grids in the dataportion and the parity portion) (408) is associated with which RAID cube(406) (assuming that the RAID controller is implementing a 3D RAIDscheme) and also which RAID grid locations (404) are associated witheach RAID grid (408).

In one embodiment of the invention, the RAID controller includes a datastructure that tracks the state (410) of each RAID grid location (404).In one embodiment of the invention, the state (410) of a RAID gridlocation may be set as filled (denoting that data (or parity data) hasbeen written to the RAID grid location) or empty (denoting that no data(or parity data) has been written to the RAID grid location). In oneembodiment of the invention, the RAID controller may also set the stateof the RAID grid location to filled if the RAID controller hasidentified data in the RAID controller to write to the RAID gridlocation (see FIG. 5, Step 506).

In one embodiment of the invention, the RAID controller includes a datastructure that tracks the RAID grid geometry. In one embodiment of theinvention, the RAID grid geometry may include, but is not limited to,the size of RAID grid and the IFD associated with each dimension of theRAID grid. This data structure (or another data structure) may alsotrack the size of the RAID cube and the IFD associated with eachdimension of the RAID cube.

In one embodiment of the invention, the RAID controller includes a datastructure that tracks the location of each P and Q parity value(including parity values within the intersection parity group (see FIG.2)) within each row and/or column within each RAID grid.

In one embodiment of the invention, the RAID controller includes a datastructure that tracks which RAID grid locations in the data portion ofthe RAID cube are used to calculate each of the P and Q parity values inthe P Parity RAID grid and Q parity RAID grid, respectively.

FIGS. 5A-5C show flowcharts in accordance with one or more embodimentsof the invention. More specifically, FIGS. 5A-5C show a method forstoring data in a storage array in accordance with one or moreembodiments of the invention. While the various steps in the flowchartare presented and described sequentially, one of ordinary skill willappreciate that some or all of the steps may be executed in differentorders, may be combined or omitted, and some or all of the steps may beexecuted in parallel. In one embodiment of the invention, the methodsshown in FIGS. 5A, 5B, and 5C may be performed in parallel.

Referring to FIG. 5A, in step 502, a request to write data is receivedfrom the client. In one embodiment of the invention, the requestincludes the <object, offset> that identifies the data from theperspective of the client. In step 504, the RAID controller, in responseto the request, writes the data to a location in the RAID controllermemory.

In step 506, the RAID controller updates one or more of the datastructures (see FIG. 4). More specifically, in one embodiment of theinvention, the RAID controller may (i) select a physical address in thestorage array in which to write the data received from the client and(ii) create a mapping between the <object, offset> for the data and theselected physical address. In one embodiment of the invention, at somepoint prior to selecting the physical address in which to write thedata, the RAID controller specifies (i) at least one RAID grid, (ii)RAID grid locations for the RAID grid, and (iii) the physical address inthe storage array associated with each RAID grid location. In addition,the RAID controller may initialize the state of each RAID grid locationto empty.

In one embodiment of the invention, FIG. 5B shows a method for writing aRAID grid to the storage array in accordance with one or moreembodiments of the invention. Referring to FIG. 5B, in step 508, adetermination is made about whether a data grid within a given RAID grid(e.g., 202 in FIG. 2) is filled. In one embodiment of the invention,this determination is made using one or more of the data structuresdescribed with respect to FIG. 4. If the data grid within a given RAIDgrid is filled, the process proceeds to step 510; otherwise, the processends.

In step 510, the P parity is calculated for each RAID grid location inthe Row P parity group (e.g., 204 in FIG. 2) using the appropriatevalues from RAID grid locations in the data grid. In step 512, the Qparity is calculated for each RAID grid location in the Row Q paritygroup (e.g., 206 in FIG. 2) using the appropriate values from RAID gridlocations in the data grid. In step 514, the P parity is calculated foreach RAID grid location in the Column P parity group (e.g., 208 in FIG.2) using the appropriate values from RAID grid locations in the datagrid. In step 516, the Q parity is calculated for each RAID gridlocation in the Column Q parity group (e.g., 210 in FIG. 2) using theappropriate values from RAID grid locations in the data grid.

In step 518, the parity values for all RAID grid locations in theintersection parity group (e.g., 212 in FIG. 2) are calculated using theappropriate values from RAID grid locations in one or more of the Row Pparity group (e.g., 204 in FIG. 2), Row Q parity group (e.g., 206 inFIG. 2), Row Q parity group (e.g., 206 in FIG. 2), and Column Q paritygroup (e.g., 210 in FIG. 2).

In step 520, the data associated with each RAID grid location for theRAID grid is written to the appropriate physical address in the storagearray. In one embodiment of the invention, the physical address in whichto write data for each of the RAID grid locations is obtained from theone or more of the data structures described with respect to FIG. 4. Instep 522, one or more data structures described with respect to FIG. 4are updated to reflect that the RAID grid has been written to thestorage array.

In one embodiment of the invention, if the RAID controller isimplementing a 3D RAID scheme, then the RAID controller may perform themethod shown in FIG. 5C. Referring to FIG. 5C, in step 524, adetermination is made about whether a data portion of the RAID cube isfilled. If the data portion of the RAID cube is filled, the processproceeds to Step 526; otherwise the process ends. In one embodiment ofthe invention, this determination is made using one or more of the datastructures described with respect to FIG. 4.

In step 526, the P parity values for each RAID grid location in the Pparity RAID grid (e.g., 312 in FIG. 3) is calculated. In one embodimentof the invention, the values for each of the RAID grid locations iscalculated using one value obtained from each of the RAID grids in thedata portion (e.g., 316 in FIG. 3) of the RAID cube.

In step 528, the Q parity values for each RAID grid location in the Qparity RAID grid (e.g., 314 in FIG. 3) is calculated. In one embodimentof the invention, the values for each of the RAID grid locations iscalculated using one value obtained from each of the RAID grids in thedata portion (e.g., 316 in FIG. 3) of the RAID cube.

In step 530, the data associated with each RAID grid location in theParity RAID grids (e.g., P Parity RAID Grid and Q Parity RAID Grid) iswritten to the appropriate physical address in the storage array. In oneembodiment of the invention, the physical address in which to write datafor each of the RAID grid locations is obtained from the one or more ofthe data structures described with respect to FIG. 4. In step 532, oneor more data structures described with respect to FIG. 4 are updated toreflect that the RAID cube has been written to the storage array.

FIGS. 6A-6C show an example of populating a RAID grid in accordance withone or more embodiments of the invention. The example is not intended tolimit the scope of the invention.

Referring to FIG. 6A, the data from the client (denoted as “D”) iswritten to the data grid (600) within the RAID grid. Once the data grid(600) is filled (as shown in FIG. 6A), the RAID controller (not shown)calculates the values for the RAID grid locations in the followinggroups: the Row P parity group (602), Row Q parity group (604), Row Qparity group (606), and Column Q parity group (608). FIG. 6B shows theRAID grid after all of the values for the aforementioned RAID gridlocations are calculated. At this stage, the only remaining values tocalculate are the values for the RAID grid locations in the IntersectionRAID group (610). FIG. 6C shows the RAID grid after all of the values inthe Intersection RAID group (610) are calculated.

In one embodiment of the invention, all values for all RAID gridlocations for a given RAID grid are stored in the RAID controller memoryprior to the RAID controller writing the RAID grid to the storage array.

FIGS. 7A-7D show an example of populating a RAID cube in accordance withone or more embodiments of the invention. The example is not intended tolimit the scope of the invention.

Consider the RAID cube depicted in FIG. 7D, which includes RAID grid A(700) RAID grid B (702), RAID grid C (704), P parity RAID grid (706),and Q parity RAID grid (708). Further, each RAID grid (700, 702, 704,706, 708) in the RAID cube includes RAID grid locations that are writtenacross IFD 1 and IFD 2 but have a constant value of IFD 3. Accordingly,in one embodiment of the invention, the value of a RAID grid location(the “target RAID grid location”) in a RAID grid may be recovered using(i) only values of RAID grid locations in the row or column in which thetarget RAID grid location is located; (ii) using values of any RAID gridlocation within the RAID grid in which the target RAID grid location islocated; or (iii) using values of any RAID grid location within the RAIDcube in which the target RAID grid location is located. Said anotherway, in one embodiment of the invention, the arrangement of the data andparity values within the RAID grid and/or RAID cube allows the value ina target RAID grid location to be recovered when there are more than twoerrors in each of the row and column in which the target RAID gridlocation is located.

Referring to FIG. 7A, FIG. 7A includes three RAID grids (700, 702, 704),which make up the data portion of the RAID cube. Each of the RAID gridlocation in each of the RAID grids (700, 702, 704) includes a 3-tupledefining the location in the storage array in which the data in the RAIDgrid location is written. In this example, the elements in the 3-tuplecorrespond to IFDs as follow: <IFD1, IFD2, IFD3>. The 3-tuplesillustrates how the locations in the storage array are selected acrossthe various IFDs. In particular, each of the RAID grid location in RAIDgrid A includes a unique combination of IFD1 and IFD2, but the samevalue for IFD3. For example, if IFD1 is a storage module, IFD2 is achannel, and IFD3 is a NAND die, then 3-tuple <4, 2,0> indicates thatthe data in the particular RAID grid location will be written to aphysical address in NAND die 1 in Storage Module 4 using Channel 2.Similarly, the 3-tuple <2, 3, 1> indicates that the data in theparticular RAID grid location will be written to a physical address inNAND 1 in Storage Module 2 using Channel 3.

RAID grid B (702) and RAID grid C (704) are arranged in a similar mannerto RAID grid A (700). However, the value for IFD3 in the 3-tuples forRAID grid locations in RAID grid B (702) is different than the value ofIFD3 in the 3-tuples for RAID grid locations for RAID grid A (700).Further, the value for IFD3 in the 3-tuples for RAID grid locations forRAID grid C (704) is different than the value of IFD3 in the 3-tuplesfor RAID grid locations for RAID grid A (700) and for RAID grid B (702).

Referring to FIG. 7B, data in each of the RAID grid locations in PParity RAID grid (706) are arranged in a similar manner to RAID grid A(700), RAID grid B (702), and RAID grid C (704). Further, as describedabove, the value of the data in each of the RAID grid locations in PParity RAID grid (706) is calculated using data from one RAID gridlocation in each of the data grids in the RAID cube (i.e., RAID grid A(700), RAID grid B (702), RAID grid C (704)). For example, the value ofthe data at RAID grid location <1, 1, 4> in the P Parity RAID grid (706)is determined by applying a P parity function (e.g., an XOR function) todata from the following RAID grid locations: (i) data from RAID grid A(700) <1,1,1>, (ii) data from RAID grid B (702) <1,1,2>, and (iii) datafrom RAID grid C (704) <1,1,3>. The values for data in the other RAIDgrid locations in P Parity RAID grid (706) are calculated in a similarmanner.

Referring to FIG. 7C, data in each of the RAID grid locations in QParity RAID grid (708) are arranged in a similar manner to RAID grid A(700), RAID grid B (702), and RAID grid C (704). Further, as describedabove, the value of the data in each of the RAID grid locations in QParity RAID grid (708) is calculated using data from one RAID gridlocation in each of the data grids in the RAID cube (i.e., RAID grid A(700), RAID grid B (702), RAID grid C (704)). For example, the value ofthe data at RAID grid location <1, 1, 5> in the Q Parity RAID grid (708)is determined by applying a Q parity function (as described above) todata from the following RAID grid locations: (i) data from RAID grid A(700)<1,1,1>, (ii) data from RAID grid B (702)<1,1,2>, and (iii) datafrom RAID grid C (704)<1,1,3>. The values for data in the other RAIDgrid locations in Q Parity RAID grid (708) are calculated in a similarmanner.

FIG. 8. shows a flow chart in accordance with one or more embodiments ofthe invention. More specifically, FIG. 8 shows a method for obtain datafrom the storage array in accordance with one or more embodiments of theinvention.

In step 800, data is obtained from a RAID grid location. In oneembodiment of the invention, the data is obtained in response to arequest from a client. In one embodiment of the invention, the requestmay specify an <object, offset> and the RAID controller may use one ormore of the data structures described with respect to FIG. 4 todetermine the physical address in the storage array at which therequested data is stored. The RAID controller may subsequently obtainthe requested data from the storage array.

In step 802, a determination is made about whether the data obtained instep 800 is corrupted. In one embodiment of the invention, the RAIDcontroller may implement any known method (e.g., checksums) fordetermining whether the data is corrupted. If the data is not corruptedthe process proceeds to step 804; otherwise the process proceeds to step806. In step 804, the data is returned to the client and the processends. In another in embodiment of the invention, if the data is unableto be obtained—for example, because the persistent storage is damaged orunplugged, or the read command fails, then process may proceed to Step806.

In step 806, the RAID controller determines from which RAID grid thedata was obtained. In step 808, the RAID controller attempts toreconstruct the data using the other RAID grid locations within the rowand/or column in which the RAID grid location that included the data islocated.

In step 810, a determination is made about whether the reconstructionattempt in step 808 was successful. In one embodiment of the invention,the RAID controller may implement any known method (e.g., checksums) fordetermining whether the reconstruction attempt was successful. If thereconstruction attempt in step 808 was successful, the process proceedsto step 812; otherwise the process proceeds to step 814. In step 812,the reconstructed data is returned to the client and the process ends.

In step 814, the RAID controller attempts to reconstruct the data usingthe other RAID grid locations in other rows and/or columns the RAIDgrid. In step 816, a determination is made about whether thereconstruction attempt in step 814 was successful. In one embodiment ofthe invention, the RAID controller may implement any known method (e.g.,checksums) for determining whether the reconstruction attempt wassuccessful. If the reconstruction attempt in step 814 was successful,the process proceeds to step 812; otherwise the process proceeds to step818.

In step 818, the RAID controller attempts to reconstruct the data usingthe other RAID grids in the RAID cube. In step 820, a determination ismade about whether the reconstruction attempt in step 818 wassuccessful. In one embodiment of the invention, the RAID controller mayimplement any known method (e.g., checksums) for determining whether thereconstruction attempt was successful. If the reconstruction attempt instep 818 was successful, the process proceeds to step 822; otherwise theprocess proceeds to step 824. In step 822, the reconstructed data isreturned to the client and the process ends. In step 824, the RAIDcontroller returns an error to the client, which indicates that therequested data cannot be retrieved from the storage array by the RAIDcontroller.

Those skilled in the art will appreciate that reconstructing the datausing the other RAID grids in the RAID cube only occurs in the eventthat the RAID controller is implementing a 3D RAID scheme.

FIGS. 9A-9D show an example in accordance with one or more embodimentsof the invention. The example is not intended to limit the scope of theinvention. Referring to FIG. 9A, consider a scenario in which a clientrequested data from RAID grid location (900). However, the data fromRAID grid location (900) is corrupted (as denoted by the shading). TheRAID controller first attempts (per step 808 in FIG. 8) to reconstructthe data in RAID grid location (900) using data from RAID grid locationin row (904) and/or column (902). However, because row (904) and column(902) each include three RAID grid locations that include corrupteddata, the data in RAID grid location (900) cannot be recovered usingonly data from row (904) and/or column (902).

Referring to FIG. 9B, the RAID controller attempts (per step 814 in FIG.8) to reconstruct the data in RAID grid location (900) using data fromother RAID grid locations in the RAID grid. In this example, the RAIDcontroller reconstructs all corrupted data in row (906). Referring toFIG. 9C, based on the reconstruction of the corrupted data in row (906),the RAID controller is able to reconstruct all corrupted data in column(908). Finally, referring to FIG. 9D, based on the reconstruction of thecorrupted data in column (908), the RAID controller is able toreconstruct the data in RAID grid location (900) using the othernon-corrupted data in row (910). In one embodiment of the invention, thereconstruction of the various corrupted data as shown in FIGS. 9B-9D areperformed as part of step 814 in FIG. 8.

Though not shown in FIGS. 9A-9D, if the data in RAID grid location (900)could not be constructed using only the data in the RAID grid, the RAIDcontroller would attempt to reconstruct the data in RAID grid location(900) (per Step 818 in FIG. 8) using data in other RAID grids within aRAID cube (not shown) if the RAID controller was implementing a 3D RAIDscheme.

Those skilled in the art will appreciate that while various examples ofthe invention has been described with respect to storing data in astorage array along IFDs and/or storing data in NAND flash, embodimentsof the invention may be implemented on any multi-dimensional disk arraywithout departing from the invention. For example, one or moreembodiments of the invention may be implemented using a two dimensionalarray of disks (magnetic, optical, solid state, or any other type ofstorage device), where data for each RAID grid location in a RAID gridis stored on a separate disk.

Further, in one embodiment of the invention, in the event that the RAIDcontroller is implementing a 3D RAID scheme using a two dimensionalarray of disks, the RAID controller may store data for each of the RAIDgrid locations using the following n-tuple: <disk x, disk y, logicalblock address (LBA) z>, where x and y are the dimensions of the diskarray. Further, for a given RAID grid the LBA is constant for each RAIDgrid location for a single RAID grid; however, the LBA is differentacross the RAID grids in the RAID cube.

The above examples for implementing embodiments of the invention using atwo-dimensional disk array are not intended to limit the scope of theinvention.

Those skilled in the art will appreciate that while the invention hasbeen described with respect to a 2D RAID scheme and a 3D RAID scheme,embodiments of the invention, may be extended to any multi-dimensionalRAID scheme.

One or more embodiments of the invention may be implemented usinginstructions executed by one or more processors in the system. Further,such instructions may corresponds to computer readable instructions thatare stored on one or more non-transitory computer readable mediums.

While the invention has been described with respect to a limited numberof embodiments, those skilled in the art, having benefit of thisdisclosure, will appreciate that other embodiments can be devised whichdo not depart from the scope of the invention as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims.

1.-29. (canceled)
 30. A non-transitory computer readable mediumcomprising instructions, which when executed perform a method forstoring data, the method comprising: receiving data from a client;calculating a first set of parity values using the data; calculating asecond set of parity values using the first set of parity values;calculating a third set of parity values using the data, the first setof parity values, and the second set of parity values; storing a portionof the data in a grid a plurality of grids,; wherein the grid comprisesa plurality of grids locations, wherein each of the plurality of gridlocations is associated a physical location in persistent storage,wherein each physical location is determined using a unique combinationof at least a first value determined using a first independent faultdomain and a second value determined using a second independent faultdomain; storing parity values from the first set of parity values thatcorrespond to the portion of the data in the grid; storing parity valuesfrom the second set of parity values that correspond to the parityvalues from the first set of parity values in the grid; and storing, inthe persistent storage, each of the third set of parity values in one ofa plurality of parity grids in the persistent storage, wherein the oneof the plurality of parity grids is associated with the grid.
 31. Thenon-transitory computer readable medium of claim 30, wherein theplurality of grids and the plurality of parity grids are associated witha (Redundant Array of Independent Disks) RAID cube.
 32. Thenon-transitory computer readable medium of claim 30, wherein the RAIDcube comprises a first dimension and a second dimension, wherein thefirst dimension is associated with the first independent fault domainand the second dimension is associated with the second independent faultdomain.
 33. The non-transitory computer readable medium of claim 32,wherein the RAID cube further comprises a third dimension that isassociated with a third independent fault domain, wherein the physicallocation is further determined using the third independent fault domain.34. The non-transitory computer readable medium of claim 33, wherein thepersistent storage comprises a plurality of storage modules, whereineach of the plurality of storage modules comprises solid state memory,and wherein the first independent fault domain is the plurality ofstorage modules, the second independent fault domain is a plurality ofchannels in each of the plurality of storage modules, wherein the thirdindependent fault domain is a plurality of NAND dies in each of theplurality of storage modules.
 35. The non-transitory computer readablemedium of claim 30, wherein the first set of parity values comprises atleast one selected from a group consisting of P parity values and Qparity values.
 36. The non-transitory computer readable medium of claim35, wherein the second set of parity values comprises intersectionparity values, wherein the intersection parity values are not calculatedusing any of the data.
 37. The non-transitory computer readable mediumof claim 30, wherein the third set of parity values comprise a groupconsisting of P parity values and Q parity values.
 38. Thenon-transitory computer readable medium of claim 30, wherein theplurality of parity grids comprises a P Parity grid and a Q Parity grid.39. The non-transitory computer readable medium of claim 30, wherein thepersistent storage comprises a plurality of storage modules, whereineach of the plurality of storage modules comprises solid state memory,and wherein the first independent fault domain is the plurality ofstorage modules and the second independent fault domain is a pluralityof channels in each of the plurality of storage modules.
 40. Thenon-transitory computer readable medium of claim 30, wherein thepersistent storage comprises a plurality of storage modules, whereineach of the plurality of storage modules comprises solid state memory,and wherein the first independent fault domain is a plurality ofchannels in each of the plurality of storage modules and the secondindependent fault domain is a plurality of NAND dies in each of theplurality of storage modules.
 41. The non-transitory computer readablemedium of claim 30, wherein each of the grids comprises a plurality ofrows, wherein a location of parity values from the first set of parityvalues are in different relative locations in at least two of theplurality of rows.
 42. The non-transitory computer readable medium ofclaim 30, wherein the plurality of parity grids do not store any of theplurality of data received from the client.
 43. A system, comprising: acontroller; a non-transitory medium operatively connected to thecontroller; persistent storage operatively connected to the controllerand comprising a plurality of storage modules, wherein each of theplurality of storage modules comprises solid state memory; wherein thenon-transitory computer readable medium comprises instructions whichwhen executed by the controller performs a method, the methodcomprising: receiving a plurality of data from a client; calculating afirst set of parity values using the plurality of data; calculating asecond set of parity values using the first set of parity values;calculating a third set of parity values using the plurality of data,the first set of parity values, and the second set of parity values;storing a portion of the data in a grid a plurality of grids, whereinthe grid comprises a plurality of grids locations, wherein each of theplurality of grid locations is associated a physical location in thepersistent storage, wherein each physical location is determined using aunique combination of at least a first value determined using a firstindependent fault domain and a second value determined using a secondindependent fault domain; storing parity values from the first set ofparity values that correspond to the portion of the data in the grid;storing parity values from the second set of parity values thatcorrespond to the parity values from the first set of parity values inthe grid; and storing, in the persistent storage, each of the third setof parity values in one of a plurality of parity grids in the persistentstorage, wherein the one of the plurality of parity grids is associatedwith the grid.
 44. The system of claim 43, further comprising: a fieldprogrammable gate array (FPGA) operatively connected to the controller,wherein calculating the first set of parity values using the datacomprises using the FPGA to calculate at least one of the first set ofparity values.
 45. The system of claim 43, wherein the controller storesa grid geometry for the grid.
 46. The system of claim 45, wherein thegrid geometry comprises a size of the grid and specifies independentfault domains associated with each dimension of the grid.
 47. The systemof claim 43, wherein the controller tracks locations parity values forthe first set of parity values in the grid.
 48. The system of claim 43,wherein the plurality of storage modules each comprises a plurality ofNAND dies.
 49. The system of claim 43, wherein the controller isconfigured to reconstruct corrupted datum in the persistent storageusing the first set of parity values, the second set of parity values,and the third set of parity values.